Method and apparatus for providing traffic information associated with map requests

ABSTRACT

A method and apparatus for enabling users who request a map of a specified route to invoke a data session to see images of the key markers and a video session to see live views of key points along the route are disclosed. If traffic appears congested, the subscriber can request an alternative route from the network along with image and video sessions to verify the traffic conditions of the alternative route.

This application is a continuation of U.S. patent application Ser. No.15/174,245, filed Jun. 6, 2016, now U.S. Pat. No. 9,823,087, which is acontinuation of U.S. patent application Ser. No. 14/507,577, filed Oct.6, 2014, now U.S. Pat. No. 9,360,327, which is a continuation of U.S.patent application Ser. No. 12/545,601, filed Aug. 21, 2009, now U.S.Pat. No. 8,855,908, which is a continuation of U.S. patent applicationSer. No. 11/261,696, filed Oct. 28, 2005, now U.S. Pat. No. 7,580,792,all of which are herein incorporated by reference in their entirety.

The present invention relates generally to communication networks and,more particularly, to a method and apparatus for providing trafficinformation associated with map requests in communication networks,e.g., Service over Internet Protocol (SoIP) networks.

BACKGROUND OF THE INVENTION

As extremely high bandwidth access networks become more accessible toresidential subscribers, they enable service providers of these networksto integrate voice, video, and data, thereby providing more conveniencefor end customers and creating new service opportunities. Due to themulti-service nature of these new services, networks need to provideadditional functionalities to end customers to support integratedcontrol of these different types of services. For instance, a subscribermay use the network to get driving directions from one place to another.However, the directions obtained do not contain any information aboutthe current traffic conditions along the recommended routes.

Therefore, a need exists for a method and apparatus for providingtraffic information associated with map requests in a packet network,e.g., a SoIP network.

SUMMARY OF THE INVENTION

In one embodiment, the present invention enables users who request a mapof a specified route to invoke a data session to see images of the keymarkers along the route, such as important turns or landmarks, and avideo session to see live views of the traffic conditions associatedwith key points in the map, such as bridges, freeways, entry and exitramps. If traffic appears congested, the subscriber can request analternative route from the network along with image and video sessionsto verify the traffic conditions of the alternative route.

BRIEF DESCRIPTION OF THE DRAWINGS

The teaching of the present invention can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates an exemplary Voice over Internet Protocol (VoIP)network related to the present invention;

FIG. 2 illustrates an exemplary Service over Internet Protocol (SoIP)network related to the present invention;

FIG. 3 illustrates an example of providing traffic informationassociated with map requests in a packet network, e.g., a SoIP network,of the present invention;

FIG. 4 illustrates a flowchart of a method for providing trafficinformation associated with map requests in a packet network, e.g., aSoIP network, of the present invention; and

FIG. 5 illustrates a high level block diagram of a general purposecomputer suitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures.

DETAILED DESCRIPTION

To better understand the present invention, FIG. 1 illustrates acommunication architecture 100 having an example network, e.g., a packetnetwork such as a VoIP network related to the present invention.Exemplary packet networks include internet protocol (IP) networks,asynchronous transfer mode (ATM) networks, frame-relay networks, and thelike. An IP network is broadly defined as a network that uses InternetProtocol to exchange data packets. Thus, a VoIP network or a SoIP(Service over Internet Protocol) network is considered an IP network.

In one embodiment, the VoIP network may comprise various types ofcustomer endpoint devices connected via various types of access networksto a carrier (a service provider) VoIP core infrastructure over anInternet Protocol/Multi-Protocol Label Switching (IP/MPLS) based corebackbone network. Broadly defined, a VoIP network is a network that iscapable of carrying voice signals as packetized data over an IP network.The present invention is described below in the context of anillustrative VoIP network. Thus, the present invention should not beinterpreted to be limited by this particular illustrative architecture.

The customer endpoint devices can be either Time Division Multiplexing(TDM) based or IP based. TDM based customer endpoint devices 122, 123,134, and 135 typically comprise of TDM phones or Private Branch Exchange(PBX). IP based customer endpoint devices 144 and 145 typically compriseIP phones or IP PBX. The Terminal Adaptors (TA) 132 and 133 are used toprovide necessary interworking functions between TDM customer endpointdevices, such as analog phones, and packet based access networktechnologies, such as Digital Subscriber Loop (DSL) or Cable broadbandaccess networks. TDM based customer endpoint devices access VoIPservices by using either a Public Switched Telephone Network (PSTN) 120,121 or a broadband access network via a TA 132 or 133. IP based customerendpoint devices access VoIP services by using a Local Area Network(LAN) 140 and 141 with a VoIP gateway or router 142 and 143,respectively.

The access networks can be either TDM or packet based. A TDM PSTN 120 or121 is used to support TDM customer endpoint devices connected viatraditional phone lines. A packet based access network, such as FrameRelay, ATM, Ethernet or IP, is used to support IP based customerendpoint devices via a customer LAN, e.g., 140 with a VoIP gateway androuter 142. A packet based access network 130 or 131, such as DSL orCable, when used together with a TA 132 or 133, is used to support TDMbased customer endpoint devices.

The core VoIP infrastructure comprises of several key VoIP components,such the Border Element (BE) 112 and 113, the Call Control Element (CCE)111, VoIP related Application Servers (AS) 114, and Media Server (MS)115. The BE resides at the edge of the VoIP core infrastructure andinterfaces with customers endpoints over various types of accessnetworks. A BE is typically implemented as a Media Gateway and performssignaling, media control, security, and call admission control andrelated functions. The CCE resides within the VoIP infrastructure and isconnected to the BEs using the Session Initiation Protocol (SIP) overthe underlying IP/MPLS based core backbone network 110. The CCE istypically implemented as a Media Gateway Controller or a softswitch andperforms network wide call control related functions as well asinteracts with the appropriate VoIP service related servers whennecessary. The CCE functions as a SIP back-to-back user agent and is asignaling endpoint for all call legs between all BEs and the CCE. TheCCE may need to interact with various VoIP related Application Servers(AS) in order to complete a call that require certain service specificfeatures, e.g. translation of an E.164 voice network address into an IPaddress.

For calls that originate or terminate in a different carrier, they canbe handled through the PSTN 120 and 121 or the Partner IP Carrier 160interconnections. For originating or terminating TDM calls, they can behandled via existing PSTN interconnections to the other carrier. Fororiginating or terminating VoIP calls, they can be handled via thePartner IP carrier interface 160 to the other carrier.

In order to illustrate how the different components operate to support aVoIP call, the following call scenario is used to illustrate how a VoIPcall is setup between two customer endpoints. A customer using IP device144 at location A places a call to another customer at location Z usingTDM device 135. During the call setup, a setup signaling message is sentfrom IP device 144, through the LAN 140, the VoIP Gateway/Router 142,and the associated packet based access network, to BE 112. BE 112 willthen send a setup signaling message, such as a SIP-INVITE message if SIPis used, to CCE 111. CCE 111 looks at the called party information andqueries the necessary VoIP service related application server 114 toobtain the information to complete this call. In one embodiment, theApplication Server (AS) functions as a SIP back-to-back user agent. IfBE 113 needs to be involved in completing the call; CCE 111 sendsanother call setup message, such as a SIP-INVITE message if SIP is used,to BE 113. Upon receiving the call setup message, BE 113 forwards thecall setup message, via broadband network 131, to TA 133. TA 133 thenidentifies the appropriate TDM device 135 and rings that device. Oncethe call is accepted at location Z by the called party, a callacknowledgement signaling message, such as a SIP 200 OK response messageif SIP is used, is sent in the reverse direction back to the CCE 111.After the CCE 111 receives the call acknowledgement message, it willthen send a call acknowledgement signaling message, such as a SIP 200 OKresponse message if SIP is used, toward the calling party. In addition,the CCE 111 also provides the necessary information of the call to bothBE 112 and BE 113 so that the call data exchange can proceed directlybetween BE 112 and BE 113. The call signaling path 150 and the callmedia path 151 are illustratively shown in FIG. 1. Note that the callsignaling path and the call media path are different because once a callhas been setup up between two endpoints, the CCE 111 does not need to bein the data path for actual direct data exchange.

Media Servers (MS) 115 are special servers that typically handle andterminate media streams, and to provide services such as announcements,bridges, transcoding, and Interactive Voice Response (IVR) messages forVoIP service applications.

Note that a customer in location A using any endpoint device type withits associated access network type can communicate with another customerin location Z using any endpoint device type with its associated networktype as well. For instance, a customer at location A using IP customerendpoint device 144 with packet based access network 140 can callanother customer at location Z using TDM endpoint device 123 with PSTNaccess network 121. The BEs 112 and 113 are responsible for thenecessary signaling protocol translation, e.g., SS7 to and from SIP, andmedia format conversion, such as TDM voice format to and from IP basedpacket voice format.

The network shown in FIG. 1 can be extended to become a SoIP networkthat supports multi-service applications including, but not limited to,video services. FIG. 2 illustrates a communication architecture 200having an example network, e.g., a packet network such as a SoIP networkrelated to the present invention. A SoIP network supports multi-serviceapplications including voice, data, and video services. In oneembodiment, a SoIP network that supports video services is describedbelow. In this SoIP network, voice services supported include, but arenot limited to, VoIP services; data services supported include, but arenot limited to, Instant Messaging (IM), electronic mail (email),internet access services, or any other IP based applications; and videoservices include, but are not limited to, Video on Demand (VoD),broadcast video, and video conferencing services.

A SoIP network that supports video services comprises an intelligentmulti-service endpoint device connected via packet access networks to aservice provider's SoIP core infrastructure employing Internet Protocol(IP) and/or Multi-Protocol Label Switching (MPLS) Protocols. Broadlydefined, a SoIP network is a network that is capable of carrying voice,video, and data signals as packetized data over an IP network. Thepresent invention is described below in the context of an illustrativeSoIP network that supports video services. Thus, the present inventionshould not be interpreted to be limited by this particular illustrativearchitecture.

Video endpoint device 232 and 233 are IP based intelligent multi-serviceendpoint device supporting voice, video, and data applications. Videoendpoint device 232 and 233 are signaling endpoints of applicationsessions, e.g. a VoIP session endpoint, an instant messaging endpoint,or a video session endpoint. In one embodiment, a video endpoint deviceis a standalone device that can be connected to home electronicappliances such as, but is not limited to, telephone 234 and 235, TV 236and 237, or Personal Computer (PC) 238 and 239. In another embodiment, avideo endpoint device can be integrated with a TV, a PC, or any homeappliances with a display.

The access networks are packet based. Packet based access networks 230and 231 use, but are not limited to, Frame Relay, ATM, Ethernet, IP, DSLor Cable broadband access network technologies to interconnect a videoendpoint device to a SoIP network that supports video services.

The core SoIP infrastructure that supports video services comprises ofseveral key components, such the Border Element (BE) 212 and 213, theCall Control Element (CCE) 211, SoIP related Application Servers (AS)214, Media Servers (MS) 215, Session Controller (SC) 241, Video ofDemand (VoD) Servers 242, Broadcast Servers (242), and Instant Messaging(IM) Servers 243. A BE resides at the edge of the SoIP coreinfrastructure and interfaces with customers endpoints over varioustypes of access networks. The functions supported by a BE include thosesupported by a BE as previously described in network 100 and FIG. 1. Inaddition, in a SoIP network that supports video services, a BE alsoserves as a gateway between a video endpoint device used by a subscriberand the SoIP core network that supports video services. All applicationsessions initiated by a SoIP subscriber must gain entry to the SoIP corenetwork via a BE. The functions supported by a CCE and a MS are the sameas those previously described in network 100 and FIG. 1. A SessionController (SC) resides within the SoIP infrastructure and is connectedto the BEs using an IP based signaling protocol such as, but is notlimited to, Session Initiation Protocol (SIP). A SC is responsible forsetting up all application session requests, such as VoIP call requests,video session requests, or data session requests, originated by acustomer within the network and interacts with, if necessary, theappropriate SoIP related AS in order to complete an application sessionthat requires certain service specific features originated by acustomer. A SC also keeps track of all sessions initiated by a customerfor session management and billing purposes as well. The functionssupported by a SoIP related AS include those supported by a VoIP AS aspreviously described in network 100 and FIG. 1. In addition, a SoIP ASalso supports all video specific application features. A VoD Server isresponsible for supporting video on demand video session requestsoriginated by a customer and sends the requested streaming videocontents, such as a movie, to the customer. A Broadcast Server isresponsible for supporting broadcast video session requested originatedby a customer and sends streaming broadcast video contents, such as TVchannels, to the customer. The VoD Server and the Broadcast Server sendsstreaming video contents to video endpoint devices using compressiontechnologies including, but are not limited to, Moving Picture ExpertsGroup (MPEG) 2, MPEG 4, MPEG 7, MPEG 21. An IM Server is responsible forsupporting IM applications involving multiple users. Instant Messagingis a form of electronic communication that involves immediate typed textcorrespondence between two or more users over the Internet who areonline simultaneously. IM is a text-based computer conference over theInternet between two or more people who are online at the same time.

In order to illustrate how the different components in a SoIP networkoperate to support video services, the following scenarios are used toillustrate how voice, data, and video sessions are setup between theSoIP network and a video endpoint. In one embodiment, a customer usingvideo endpoint device 232 at location A places a VoD session request tothe SoIP network that supports video services using TV 236. During thesession initiation, a setup signaling message is sent from videoendpoint device 232 to BE 212 using signaling path segment 250. BE 212will then send a setup signaling message, such as a SIP-INVITE messageif SIP is used, to SC 241 using signaling path segment 251. SC 241processes the session requests and forwards the request to theappropriate server for further processing. In this case, the request isa VoD session; therefore, the request will be forwarded to VoD Server242 using signaling path segment 252. SC 241 may interact with AS 214using signaling path segment 259 to verify customer's subscriptioninformation or to retrieve video specific applications or data in orderto complete the session request. Once the VoD session is verified, VoDServer 242 sends the requested VoD streaming contents to BE 212 usingdata path segment 262. BE 212 then forwards the requested VoD streamingcontents to video endpoint 232 using data path segment 260. Similarly, acustomer at location Z using TV 237 connected to video endpoint 233 canrequest a VoD session via SC 241 with streaming VoD contents sent by VoDServer 242. Note that a VoD server may be placed closer to end users ina packet access network to serve video endpoints in an alternativeembodiment.

In another embodiment, a customer using video endpoint device 232 atlocation A places a broadcast video session request to the SoIP networkthat supports video services using TV 236. During the sessioninitiation, a setup signaling message is sent from video endpoint device232 to BE 212 using signaling path segment 250. BE 212 will then send asetup signaling message, such as a SIP-INVITE message if SIP is used, toSC 241 using signaling path segment 251. SC 241 processes the sessionrequests and forwards the request to the appropriate server for furtherprocessing. In this case, the request is a broadcast video session for aparticular premium TV channel; therefore, the request will be forwardedto Broadcast Server 243 using signaling path segment 253. SC 241 mayinteract with AS 214 using signaling path segment 259 to verifycustomer's subscription information or to retrieve video specificapplications or data in order to complete the session request. Once thebroadcast session is verified, Broadcast Server 243 sends the requestedbroadcast video streaming contents to BE 212 using data path segment263. BE 212 then forwards the requested broadcast video streamingcontents to video endpoint 232 using data path segment 260. Similarly, acustomer at location Z using TV 237 connected to video endpoint 233 canrequest a broadcast video session via SC 241 with streaming broadcastvideo contents sent by Broadcast Server 243. Note that a Broadcastserver may be placed closer to end users in a packet access network toserve video endpoints in an alternative embodiment.

In another embodiment, a customer using video endpoint device 232 atlocation A places an IM session request to the video network using PC238. During the session initiation, a setup signaling message is sentfrom video endpoint device 232 to BE 212 using signaling path segment250. BE 212 will then send a setup signaling message, including loginand password information of the user, to SC 241 using signaling pathsegment 251. SC 241 processes the session requests and forwards therequest to the appropriate server for further processing. In this case,the request to sign on an IM session; therefore, the request will beforwarded to IM Server 244 using signaling path segment 254. SC 241 mayinteract with AS 214 using signaling path segment 259 to verifycustomer's subscription information or to retrieve IM specificapplications or data in order to complete the session request. Once theIM session is verified, IM Server 244 establishes the requested IM datapath to video endpoint 232 via BE 212 using data path comprising datapath segment 260 and 264. Similarly, a customer at location A using TV236 connected to video endpoint 232 or a customer at location Z using PC239 or TV 237 connected to video endpoint 233 can request an IM sessionvia SC 241 with IM functions provided by IM Server 244.

In another embodiment, a customer using video endpoint device 232 atlocation A places a VoIP session request destined to video endpointdevice 233 via the SoIP network that supports video services usingtelephone 234. During the session initiation, a setup signaling messageis sent from video endpoint device 232 to BE 212 using signaling pathsegment 250. BE 212 will then send a setup signaling message, such as aSIP-INVITE message if SIP is used, to SC 241 using signaling pathsegment 251. SC 241 processes the session requests and forwards therequest to the appropriate server for further processing. In this case,the request is a VoIP session for a call destined to a called party atlocation Z; therefore, the request will be forwarded to CCE 211 usingsignaling path segment 255. CCE may interact with AS 214 using signalingpath segment 259 to verify customer's subscription information or toretrieve VoIP specific applications or data in order to complete thesession request. The signaling flows to establish a VoIP call betweenvideo endpoint device 232 and 233 is similar to those describedpreviously in network 100 and FIG. 1. In one embodiment, the ApplicationServer (AS) functions as a SIP back-to-back user agent. Since BE 213needs to be involved in completing the call; CCE 211 sends another callsetup message, such as a SIP-INVITE message if SIP is used, to BE 213using signaling path segment 257. Upon receiving the call setup message,BE 213 forwards the call setup message, via packet access network 231 tovideo endpoint device 233 using signaling path segment 258. Videoendpoint device 233 then identifies telephone 235 and rings thattelephone. Once the call is accepted at location Z by the called party,a call acknowledgement signaling message, such as a SIP 200 OK responsemessage if SIP is used, is sent in the reverse direction back to the CCE211. After the CCE 211 receives the call acknowledgement message, itwill then send a call acknowledgement signaling message, such as a SIP200 OK response message if SIP is used, toward the calling party atlocation A using signaling path comprising signaling path segment 256and 250 via BE 212. In addition, the CCE 211 also provides the necessaryinformation of the call to both BE 212 and BE 213 so that the call dataexchange can proceed directly between BE 212 and BE 213. CCE 211 alsoprovides the call completion status of a VoIP call to SC 241. The callmedia path comprising media path segment 260, 261, and 265 areillustratively shown in FIG. 2. Note that the call signaling path andthe call media path are different because once a call has been setup upbetween two video endpoint devices, SC 241 and CCE 211 does not need tobe in the data path for actual direct data exchange.

As extremely high bandwidth access networks become more accessible toresidential subscribers, they enable service providers of these networksto integrate voice, video, and data, thereby providing more conveniencefor end customers and creating new service opportunities. Due to themulti-service nature of these new services, networks need to provideadditional functionalities to end customers to support integratedcontrol of these different types of services. For instance, a subscribermay use the network to get driving directions from one place to another.However, the directions obtained do not contain any information aboutthe current traffic conditions along the recommended routes.

To address this need, the present invention enables users who request amap of a specified route to invoke a data session to see images of thekey markers along the route, such as important turns or landmarks, and avideo session to see live views of the traffic conditions associatedwith key points in the map, such as bridges, freeways, entry and exitramps. If traffic appears congested, the subscriber can request analternative route from the network along with image and video sessionsto verify the traffic conditions of the alternative route.

FIG. 3 illustrates an example 300 of providing traffic informationassociated with map requests in a packet network, e.g., a SoIP network,of the present invention. In FIG. 3, subscriber 371 uses TV 339 as aconsole to request map and traffic application session from the network.The request is sent by video endpoint device 332 to SC 341 using flow350. Upon receiving the map and traffic application session request, SC341 finds out that the request is a map and traffic session request andforwards the request to Map and Traffic Application Server 342 usingflow 351 to establish a map and traffic application session betweensubscriber 371 and Map and Traffic Application Server 342.

Once the session is established, subscriber 371 can provide the sourceand destination pair information to Map and Traffic Application Server342 using flow 361. Then, Map and Traffic Application Server 342determines a primary route (e.g., a recommended route) for the mapdirections request based on the received source and destination pairinformation. Map and Traffic Application Server 342 sends the determinedprimary route to subscriber 371 for review. Note the returned primaryroute comprises key markers and key points along the determined routethat can be activated by subscriber 371 to view current trafficconditions at the locations (e.g., an intersection of roads, a landmark(e.g., an airport, a bus terminal or a bus stop), a bridge, a tunnel, afreeway entry ramp, a freeway exit ramp, a toll plaza, a bordercrossing, and the like) represented by those key markers and key points.If subscriber 371 clicks on a key marker on the map, a current image ofthe location represented by the key marker will be sent to subscriber371 using flow 361 for review. The current image is sent via a datasession by Map and Traffic Application Server 342 to subscriber 371. Ifsubscriber clicks on a key point on the map, a current live video of thelocation represented by the key point will be sent to subscriber 371using flow 361 for review. The current live video is sent via a videosession by Map and Traffic Application Server 342 to subscriber 371. Ifsubscriber 371 finds out that the traffic conditions at a key marker orkey point location is congested or for any other reasons, subscriber 371can request Map and Traffic Application Server 342 to provide analternative route instead. Then subscriber 371 can review thealternative route (e.g., a recommended route) and traffic conditionsassociated with the alternative route to determine the directions to usefor a trip.

FIG. 4 illustrates a flowchart of a method 400 for providing trafficinformation associated with map requests in a packet network, e.g., aSoIP network, of the present invention. Method 400 starts in step 405and proceeds to step 410.

In step 410, the method receives a map and traffic application sessionrequest from a subscriber. For example, the map and traffic applicationrequest is received by a SC.

In step 415, the method establishes a map and traffic applicationsession to the subscriber. The SC forwards the request to a Map andTraffic Application Server to establish the requested session betweenthe subscriber and the Map and Traffic Application Server.

In step 420, the method receives the source and destination pairinformation (e.g., a source location and a destination location) of aroute from the subscriber. The source and destination pair informationis received by the Map and Traffic Application Server.

In step 425, the method determines a primary route for the mapdirections request. The primary route is determined by the Map andTraffic Application Server.

In step 430, the method sends the determined route map comprising keymarkers and/or key points along the route to the subscriber. Thedetermined route map is sent by the Map and Traffic Application Serverand is displayed in an independent display frame on a video displaydevice currently used by the subscriber.

In step 435, the method checks if a key marker or a key point displayedalong the determined route is activated by the subscriber. Theactivation of a key marker or a key point is received by the Map andTraffic Application Server. A key marker or a key point can be activatedby clicking the marker or point using a pointer device, such as acomputer mouse. A key marker on the map provides a current image of thelocation represented by the key marker. A key point on the map providesaccess to a current live video of the location represented by the keypoint. If a marker or point is activated by the subscriber, the methodproceeds to step 440; otherwise, the method proceeds to step 445.

In step 440, the method sends a current image of the locationrepresented by the key marker to the subscriber, if a key marker isactivated. The method sends a current live video of the locationrepresented by the key point to the subscriber, if a key point isactivated. The current image is sent by the Map and Traffic ApplicationServer using a data session to the subscriber and the current live videois sent by the Map and Traffic Application Server using a video session.

In step 445, the method checks if the method receives an alternative mapand traffic route request from the subscriber. The request is receivedby the Map and Traffic Application Server. If a request is received, themethod proceeds to step 450; otherwise, the method proceeds to step 460.

In step 450, the method determines an alternative route for the map andtraffic request. The alternative route is determined by the Map andTraffic Application Server. The method proceeds back to step 430. Themethod ends in step 460.

FIG. 5 depicts a high level block diagram of a general purpose computersuitable for use in performing the functions described herein. Asdepicted in FIG. 5, the system 500 comprises a processor element 502(e.g., a CPU), a memory 504, e.g., random access memory (RAM) and/orread only memory (ROM), a module 505 for providing traffic informationassociated with map requests, and various input/output devices 506(e.g., storage devices, including but not limited to, a tape drive, afloppy drive, a hard disk drive or a compact disk drive, a receiver, atransmitter, a speaker, a display, a speech synthesizer, an output port,and a user input device (such as a keyboard, a keypad, a mouse, and thelike)).

It should be noted that the present invention can be implemented insoftware and/or in a combination of software and hardware, e.g., usingapplication specific integrated circuits (ASIC), a general purposecomputer or any other hardware equivalents. In one embodiment, thepresent module or process 505 for providing traffic informationassociated with map requests can be loaded into memory 504 and executedby processor 502 to implement the functions as discussed above. As such,the present process 505 for providing traffic information associatedwith map requests (including associated data structures) of the presentinvention can be stored on a computer readable medium or carrier, e.g.,RAM memory, magnetic or optical drive or diskette and the like.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A method for requesting a recommended route in acommunication network, the method comprising: sending, by a processor ofa subscriber device, a request for establishing an application sessionvia the communication network, where the application session is forreceiving the recommended route, wherein the request comprises a sourcelocation and a destination location; and receiving, by the processor,the recommended route from the communication network, where therecommended route comprises a key point representing a location alongthe recommended route where a live image of the location is availablefor viewing, wherein the recommended route traverses between the sourcelocation and the destination location.
 2. The method of claim 1, whereinthe sending comprises sending the request via the communication networkthat comprises an internet protocol network.
 3. The method of claim 1,wherein the application session is established between a map and trafficapplication server and the subscriber device via a session controller.4. The method of claim 3, wherein the recommended route is determined bythe map and traffic application server.
 5. The method of claim 1,further comprising: sending, by the processor, another request for analternative route.
 6. The method of claim 1, wherein the applicationsession is provided to an independent display frame on a display of thesubscriber device.
 7. The method of claim 1, wherein the locationcomprises a bridge.
 8. The method of claim 1, wherein the locationcomprises a freeway.
 9. The method of claim 1, wherein the locationcomprises an entry ramp.
 10. The method of claim 1, wherein the locationcomprises an exit ramp.
 11. A tangible computer-readable medium storinginstructions which, when executed by a processor of a subscriber device,cause the processor to perform operations for receiving a recommendedroute in a communication network, the operations comprising: sending arequest for establishing an application session via the communicationnetwork, where the application session is for receiving the recommendedroute, wherein the request comprises a source location and a destinationlocation; and receiving the recommended route from the communicationnetwork, where the recommended route comprises a key point representinga location along the recommended route where a live image of thelocation is available for viewing, wherein the recommended routetraverses between the source location and the destination location. 12.The tangible computer-readable medium of claim 11, wherein the sendingcomprises sending the request via the communication network thatcomprises an internet protocol network.
 13. The tangiblecomputer-readable medium of claim 11, wherein the application session isestablished between a map and traffic application server and thesubscriber device via a session controller.
 14. The tangiblecomputer-readable medium of claim 11, the operations further comprising:sending another request for an alternative route.
 15. The tangiblecomputer-readable medium of claim 11, wherein the application session isprovided to an independent display frame on a display of the subscriberdevice.
 16. The tangible computer-readable medium of claim 11, whereinthe location comprises a bridge.
 17. The tangible computer-readablemedium of claim 11, wherein the location comprises a freeway.
 18. Thetangible computer-readable medium of claim 11, wherein the locationcomprises an entry ramp.
 19. The tangible computer-readable medium ofclaim 11, wherein the location comprises an exit ramp.
 20. An apparatusfor receiving a recommended route in a communication network, theapparatus comprising: a processor; and a tangible computer-readablemedium storing instructions which, when executed by the processor, causethe processor to perform operations, the operations comprising: sendinga request for establishing an application session via the communicationnetwork, where the application session is for receiving the recommendedroute, wherein the request comprises a source location and a destinationlocation; and receiving the recommended route from the communicationnetwork, where the recommended route comprises a key point representinga location along the recommended route where a live image of thelocation is available for viewing, wherein the recommended routetraverses between the source location and the destination location.